bitkeeper revision 1.1767 (42c18c1dNRHfk7ZFajLHHtesQcrKlg)

At the time of debugging the fs segment problem, I noticed this bug (and
was able to test it).

Signed-off-by: Jun Nakajima <jun.nakajima@intel.com>

diff --git a/linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/entry.S b/linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/entry.S
index 0285860d73df80dcf4fc535dcce8cc65e94f304c..efc178ae47de588db272e561a0f5b5ba1e7e0fd9 100644 (file)
--- a/linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/entry.S
+++ b/linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/entry.S
@@ -769,11 +769,11 @@ ENTRY(failsafe_callback)
 .section .fixup,"ax";  \
 6:     movq $0,(%rsp); \
        jmp 1b;         \
-7:     movq $0,(%rsp); \
+7:     movq $0,8(%rsp);        \
        jmp 2b;         \
-8:     movq $0,(%rsp); \
+8:     movq $0,16(%rsp);       \
        jmp 3b;         \
-9:     movq $0,(%rsp); \
+9:     movq $0,24(%rsp);       \
        jmp 4b;         \
 .previous;             \
 .section __ex_table,"a";\